feat: add custom OpenTelemetry collector endpoints support #7023

roomote · 2025-08-12T21:15:35Z

Implements #7020 - Adds the ability to configure custom OpenTelemetry (OTEL) collector endpoints for telemetry traces.

Summary

This PR adds support for configuring custom OpenTelemetry collector endpoints, allowing power users to send telemetry traces to their own collectors for visibility into model/inference activity.

Changes

Core Implementation

OpenTelemetryClient: New telemetry client class in packages/telemetry/src/OpenTelemetryClient.ts that:
- Supports multiple OTEL endpoints with custom headers
- Respects VSCode telemetry settings and user opt-in preferences
- Uses batch processing for better performance
- Includes error handling to prevent disrupting the application

Configuration

Added otelEnabled and otelEndpoints fields to the global settings schema
Endpoints support URL, custom headers, and individual enable/disable toggles

User Interface

Created OpenTelemetrySettings component in the settings view
Features include:
- Enable/disable toggle for OpenTelemetry
- Add/remove multiple endpoints
- Configure endpoint URLs and custom headers
- Collapsible UI for better organization
- Per-endpoint enable/disable toggles

Integration

Integrated OTEL client initialization in extension startup
Added message handlers for OTEL settings updates between webview and extension
OTEL client is registered with the telemetry service when enabled

Testing

Comprehensive test suite for OpenTelemetryClient covering:
- Initialization with multiple endpoints
- Event capture and span creation
- Telemetry state management
- Error handling
- Shutdown procedures

Testing Instructions

Open the Roo Code settings
Navigate to the OpenTelemetry section
Enable OpenTelemetry and add a collector endpoint
Configure the endpoint URL (e.g., https://otel-collector.example.com/v1/traces)
Optionally add custom headers for authentication
Save settings and restart VS Code
Telemetry traces will be sent to the configured endpoints

Notes

Changes to endpoints require restarting VS Code to take effect
The implementation respects VSCode global telemetry settings
All tests pass successfully

Closes #7020

Important

Adds support for custom OpenTelemetry collector endpoints, allowing users to configure and send telemetry traces to their own endpoints.

Behavior:
- Adds OpenTelemetryClient in OpenTelemetryClient.ts to handle telemetry with custom OTEL endpoints.
- Supports multiple endpoints, custom headers, and respects VSCode telemetry settings.
- Batch processing and error handling included.
Configuration:
- Adds otelEnabled and otelEndpoints to global settings schema in global-settings.ts.
- Endpoints can be individually enabled/disabled with custom headers.
User Interface:
- Adds OpenTelemetrySettings component in OpenTelemetrySettings.tsx for configuring OTEL settings.
- UI includes toggles for enabling OTEL and managing endpoints.
Integration:
- Initializes OpenTelemetryClient in extension.ts if enabled in settings.
- Updates webviewMessageHandler.ts to handle OTEL settings updates.
Testing:
- Adds tests in OpenTelemetryClient.test.ts for initialization, event capture, and error handling.
Misc:
- Updates package.json to include OpenTelemetry dependencies.

^{This description was created by}^{for bb00d6c. You can customize this summary. It will automatically update as commits are pushed.}

- Add OpenTelemetryClient class to packages/telemetry for sending traces to custom OTEL endpoints - Add OTEL configuration fields (otelEnabled, otelEndpoints) to global settings schema - Create UI components in settings view for managing OTEL endpoints with add/remove/edit capabilities - Integrate OTEL client initialization in extension startup - Add message handlers for OTEL settings updates between webview and extension - Include comprehensive test coverage for OpenTelemetryClient - Support multiple endpoints with custom headers and enable/disable toggles per endpoint Implements #7020

ellipsis-dev · 2025-08-12T21:18:01Z

webview-ui/src/components/settings/OpenTelemetrySettings.tsx

+	setCachedStateField: SetCachedStateField<"otelEnabled" | "otelEndpoints">
+}
+
+export const OpenTelemetrySettings = ({


Consider using the i18n translation function (e.g. t('...')) for all user‐visible strings like 'OpenTelemetry', 'Add Endpoint', and 'Collector Endpoints' to ensure consistency with the rest of the app.

^{This comment was generated because it violated a code review rule: irule_C0ez7Rji6ANcGkkX.}

ellipsis-dev · 2025-08-12T21:18:01Z

packages/telemetry/src/OpenTelemetryClient.ts

+
+			// Create resource with service information
+			const version =
+				vscode?.extensions?.getExtension?.("rooveterinaryinc.roo-cline")?.packageJSON?.version || "unknown"


The extension identifier "rooveterinaryinc.roo-cline" might be a typographical error. Should it be "rooveterinaryinc.roo-code" or another identifier? Please confirm.

Suggested change

vscode?.extensions?.getExtension?.("rooveterinaryinc.roo-cline")?.packageJSON?.version || "unknown"

vscode?.extensions?.getExtension?.("rooveterinaryinc.roo-code")?.packageJSON?.version || "unknown"

roomote

Reviewing my own code because apparently I trust no one, not even myself.

roomote · 2025-08-12T21:25:19Z

packages/telemetry/src/OpenTelemetryClient.ts

+
+			// Create resource with service information
+			const version =
+				vscode?.extensions?.getExtension?.("rooveterinaryinc.roo-cline")?.packageJSON?.version || "unknown"


Is this extension ID intentional? I noticed it's hardcoded as 'rooveterinaryinc.roo-cline' - should this perhaps be updated to match the actual extension ID or made configurable?

roomote · 2025-08-12T21:25:19Z

packages/telemetry/src/OpenTelemetryClient.ts

+	}
+}
+
+export interface OtelEndpoint {


Consider adding JSDoc comments for the OtelEndpoint interface properties to clarify what each field represents:

roomote · 2025-08-12T21:25:20Z

packages/telemetry/src/OpenTelemetryClient.ts

+
+			// Add exporters for each endpoint
+			for (const endpoint of this.endpoints) {
+				const exporter = new OTLPTraceExporter({


Would it be beneficial to add retry logic here for transient network failures? Other telemetry implementations in the codebase seem to have retry mechanisms.

roomote · 2025-08-12T21:25:20Z

webview-ui/src/components/settings/OpenTelemetrySettings.tsx

+																	URL
+																</label>
+																<VSCodeTextField
+																	value={endpoint.url}


Consider adding basic URL validation here to prevent configuration errors. Something like:

Then you could show a validation error if the URL is invalid.

roomote · 2025-08-12T21:25:20Z

webview-ui/src/components/settings/OpenTelemetrySettings.tsx

+						)}
+
+						<div className="text-vscode-descriptionForeground text-sm mt-2">
+							<strong>Note:</strong> Changes to endpoints require restarting VS Code to take effect.


The restart requirement note is important but might be missed at the bottom. Consider making it more prominent, perhaps showing a notification when settings are saved, or moving this warning to the top of the section?

daniel-lxs · 2025-08-15T18:56:29Z

Author interested in implementing this

roomote bot requested review from mrubens, cte and jr as code owners August 12, 2025 21:15

github-project-automation bot added this to Roo Code Roadmap and Roo Code Roadmap Aug 12, 2025

github-project-automation bot moved this to Triage in Roo Code Roadmap Aug 12, 2025

github-project-automation bot moved this to New in Roo Code Roadmap Aug 12, 2025

dosubot bot added size:XXL This PR changes 1000+ lines, ignoring generated files. enhancement New feature or request UI/UX UI/UX related or focused labels Aug 12, 2025

roomote bot mentioned this pull request Aug 12, 2025

Add the ability to add custom OTEL collector endpoints #7020

Open

4 tasks

ellipsis-dev bot reviewed Aug 12, 2025

View reviewed changes

roomote bot commented Aug 12, 2025

View reviewed changes

hannesrudolph added the Issue/PR - Triage New issue. Needs quick review to confirm validity and assign labels. label Aug 12, 2025

daniel-lxs moved this from Triage to PR [Needs Prelim Review] in Roo Code Roadmap Aug 15, 2025

hannesrudolph added PR - Needs Preliminary Review and removed Issue/PR - Triage New issue. Needs quick review to confirm validity and assign labels. labels Aug 15, 2025

daniel-lxs closed this Aug 15, 2025

github-project-automation bot moved this from New to Done in Roo Code Roadmap Aug 15, 2025

github-project-automation bot moved this from PR [Needs Prelim Review] to Done in Roo Code Roadmap Aug 15, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat: add custom OpenTelemetry collector endpoints support #7023

feat: add custom OpenTelemetry collector endpoints support #7023

Uh oh!

roomote bot commented Aug 12, 2025 •

edited by ellipsis-dev bot

Loading

Uh oh!

ellipsis-dev bot Aug 12, 2025

Uh oh!

ellipsis-dev bot Aug 12, 2025

Uh oh!

roomote bot left a comment

Uh oh!

roomote bot Aug 12, 2025

Uh oh!

roomote bot Aug 12, 2025

Uh oh!

roomote bot Aug 12, 2025

Uh oh!

roomote bot Aug 12, 2025

Uh oh!

roomote bot Aug 12, 2025

Uh oh!

daniel-lxs commented Aug 15, 2025

Uh oh!

Uh oh!

	vscode?.extensions?.getExtension?.("rooveterinaryinc.roo-cline")?.packageJSON?.version \|\| "unknown"
	vscode?.extensions?.getExtension?.("rooveterinaryinc.roo-code")?.packageJSON?.version \|\| "unknown"

feat: add custom OpenTelemetry collector endpoints support #7023

feat: add custom OpenTelemetry collector endpoints support #7023

Uh oh!

Conversation

roomote bot commented Aug 12, 2025 • edited by ellipsis-dev bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Changes

Core Implementation

Configuration

User Interface

Integration

Testing

Testing Instructions

Notes

Uh oh!

ellipsis-dev bot Aug 12, 2025

Choose a reason for hiding this comment

Uh oh!

ellipsis-dev bot Aug 12, 2025

Choose a reason for hiding this comment

Uh oh!

roomote bot left a comment

Choose a reason for hiding this comment

Uh oh!

roomote bot Aug 12, 2025

Choose a reason for hiding this comment

Uh oh!

roomote bot Aug 12, 2025

Choose a reason for hiding this comment

Uh oh!

roomote bot Aug 12, 2025

Choose a reason for hiding this comment

Uh oh!

roomote bot Aug 12, 2025

Choose a reason for hiding this comment

Uh oh!

roomote bot Aug 12, 2025

Choose a reason for hiding this comment

Uh oh!

daniel-lxs commented Aug 15, 2025

Uh oh!

Uh oh!

roomote bot commented Aug 12, 2025 •

edited by ellipsis-dev bot

Loading